CVE-2023-52864
Intel WMI Memory Corruption Vulnerability
Description
In the Linux kernel, the following vulnerability has been resolved: platform/x86: wmi: Fix opening of char device Since commit fa1f68db6ca7 ("drivers: misc: pass miscdevice pointer via file private data"), the miscdevice stores a pointer to itself inside filp->private_data, which means that private_data will not be NULL when wmi_char_open() is called. This might cause memory corruption should wmi_char_open() be unable to find its driver, something which can happen when the associated WMI device is deleted in wmi_free_devices(). Fix the problem by using the miscdevice pointer to retrieve the WMI device data associated with a char device using container_of(). This also avoids wmi_char_open() picking a wrong WMI device bound to a driver with the same name as the original driver.
INFO
Published Date :
May 21, 2024, 4:15 p.m.
Last Modified :
Nov. 21, 2024, 8:40 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Solution
- Update the affected kernel packages.
- Update the affected packages.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-52864.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-52864 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-52864
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-52864 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-52864 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/36d85fa7ae0d6be651c1a745191fa7ef055db43e Added Reference https://git.kernel.org/stable/c/44a96796d25809502c75771d40ee693c2e44724e Added Reference https://git.kernel.org/stable/c/9fb0eed09e1470cd4021ff52b2b9dfcbcee4c203 Added Reference https://git.kernel.org/stable/c/cf098e937dd125c0317a0d6f261ac2a950a233d6 Added Reference https://git.kernel.org/stable/c/d426a2955e45a95b2282764105fcfb110a540453 Added Reference https://git.kernel.org/stable/c/e0bf076b734a2fab92d8fddc2b8b03462eee7097 Added Reference https://git.kernel.org/stable/c/eba9ac7abab91c8f6d351460239108bef5e7a0b6 Added Reference https://git.kernel.org/stable/c/fb7b06b59c6887659c6ed0ecd3110835eecbb6a3 -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 29, 2024
Action Type Old Value New Value -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 21, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: platform/x86: wmi: Fix opening of char device Since commit fa1f68db6ca7 ("drivers: misc: pass miscdevice pointer via file private data"), the miscdevice stores a pointer to itself inside filp->private_data, which means that private_data will not be NULL when wmi_char_open() is called. This might cause memory corruption should wmi_char_open() be unable to find its driver, something which can happen when the associated WMI device is deleted in wmi_free_devices(). Fix the problem by using the miscdevice pointer to retrieve the WMI device data associated with a char device using container_of(). This also avoids wmi_char_open() picking a wrong WMI device bound to a driver with the same name as the original driver. Added Reference kernel.org https://git.kernel.org/stable/c/cf098e937dd125c0317a0d6f261ac2a950a233d6 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/9fb0eed09e1470cd4021ff52b2b9dfcbcee4c203 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/d426a2955e45a95b2282764105fcfb110a540453 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e0bf076b734a2fab92d8fddc2b8b03462eee7097 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/44a96796d25809502c75771d40ee693c2e44724e [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/36d85fa7ae0d6be651c1a745191fa7ef055db43e [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/fb7b06b59c6887659c6ed0ecd3110835eecbb6a3 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/eba9ac7abab91c8f6d351460239108bef5e7a0b6 [No types assigned]